Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NU-1683] Fixes memory leak in test mechanism introduced in #4956 #6337

Merged

Conversation

arkadius
Copy link
Member

@arkadius arkadius commented Jul 8, 2024

Describe your changes

Checklist before merge

  • Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
  • Code is cleaned from temporary changes and commented out lines
  • Parts of the code that are not easy to understand are documented in the code
  • Changes are covered by automated tests
  • Showcase in dev-application.conf added to demonstrate the feature
  • Documentation added or updated
  • Added entry in Changelog.md describing the change from the perspective of a public distribution user
  • Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
  • Verify that PR will be squashed during merge

@arkadius arkadius force-pushed the nu-1683-testmechanism-memoryleak-fix branch from 205db19 to 352d1fa Compare July 8, 2024 11:31
@github-actions github-actions bot added the docs label Jul 8, 2024
@arkadius arkadius force-pushed the nu-1683-testmechanism-memoryleak-fix branch from 352d1fa to 02037e7 Compare July 8, 2024 11:32
@arkadius arkadius force-pushed the nu-1683-testmechanism-memoryleak-fix branch from 02037e7 to e3505e4 Compare July 8, 2024 11:40
@lukasz-bigorajski lukasz-bigorajski merged commit 7869498 into release/1.16 Jul 8, 2024
18 checks passed
@lukasz-bigorajski lukasz-bigorajski deleted the nu-1683-testmechanism-memoryleak-fix branch July 8, 2024 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants